This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
[NSF versus a relational DB
Add these requirements to the "employee" example you gave:
- granular field-level security to access certian employee-specific data
- replication (especially offline)
- each employee has a variable number of user-defined fields for tracking metadata]
you are talking about things that already exist for a while. there is nothing new (and exceptional) in the application dev area for years (Except DB2NSF).
[...and all of a sudden NSF is much more attractive. Read my blog entries -- there is a lot that you can build into Notes (though, yes, it would be nice if it was supported natively) that makes it behave more like a true relational database.]
if the server core doesn's support the functionality you canot really simulate it. DB2 is relational and supports transactions, so you have the infrastructure to start something.
[In my experience it's much harder to make a relational database as flexible as NSF. IBM learned this the hard way. After years of trying to migrate NSF to DB2 (NSF<>DB2 was a step towards that final destination) IBM decided to quit doing it.]
replication between databases exists for a while.
security is also implemented thru some frameworks like Acegi.
since db2 viper there are also new enhancements for manupulating unstructured data like XML (or DXL should I say !)
For sure, it is not as easy as domino but in regards of what i observe from IBM, making NSF relational seems impossible.
[Keep in mind that IBM has said they are no longer moving forward on enhancing NSF/DB2, but they simultaneously said that they ARE moving forward on enhancing NSF. And they know that people want relational-type capabilities.]
IBM says something today another thing tomorrow. I simply have the impression that they don't know what to do and worst, where to go. (once again in the dev app area)
All the innovative strategy is focused on messaging and nothing happens in the dev part. (ok there are 3 new @functions !!).
They spend time developing something (garnet, workplace, db2nsf...) and then they throw it away. this is a major technical/strategical problem which happens every 2 or 3 years with them (I don't imagine the reaction of people deeply involved in these projects, they must be disgusted)
It seems that the captain changes every hour and cancels previous orders for giving new ones. the ship is zigzaging and the passengers are sick !
what I'm saying is quite easy - they should decide what they want and stop playing with the community like that
A) transform Domino to a full SOA messaging (or even /repository) platform. (it's the actual path)
or
B) transform Domino to a real application server platform (which means AT LEAST, relational capabilities), but it seems too difficult for them, or maybe they really don't want to compete with internal softs (websphere / portal / db2 / tivoli ).
if this is not done, Domino is doomed to decline little by little .... what is actually happening (at least in the Application server area)
ps : come on, we are in 2009... IBM should say : YES WE CAN :))
Feedback response number WEBB7NWJAJ created by ~Judy Destookonyetsi on 02/03/2009
YES WE CAN :))
Return to top
. . . . . . . . . . YES WE CAN :)) (~Judy Destookon... 3.Feb.09) 
